tests/distributors/distribution-factory.test.ts:127

• This test asserts legacy Adopt distributions return null, but the PR description/issue calls for a fail-fast error with explicit migration guidance. If getJavaDistribution is updated to throw (instead of returning null), this test should assert on the error message and the correct replacement distribution.

  it.each(['adopt', 'adopt-hotspot', 'adopt-openj9'])(
    'does not support legacy Adopt distribution %s',
    async distributionName => {
      expect(
        await getJavaDistribution(distributionName, installerOptions('jdk'))
      ).toBeNull();
    }

src/distributions/distribution-factory.ts:32

• Legacy Adopt distributions currently fall through to default: return null, which then turns into the generic error No supported distribution was found for input ... in src/setup-java.ts. The PR description/issue requires a hard, fail-fast error that tells users exactly what to migrate to (adopt/adopt-hotspot -> temurin, adopt-openj9 -> semeru).

  switch (distributionName) {
    case JavaDistribution.JdkFile: {
      const {LocalDistribution} = await import('./local/installer.js');
      return new LocalDistribution(normalizedInstallerOptions, jdkFile);
    }

README.md:36

• The docs now state legacy Adopt distributions were removed, but .tool-versions parsing still silently remaps the asdf vendor prefix adoptopenjdk to temurin (see src/util.ts mapAsdfDistribution: adoptopenjdk: 'temurin'). This contradicts the PR description/issue requirement to remove .tool-versions adoptopenjdk* remapping and fail with a hard error instructing users to pick temurin or semeru explicitly (especially for adoptopenjdk-openj9, which currently collapses to adoptopenjdk and would map to Temurin).

- **Legacy AdoptOpenJDK distributions were removed.** Replace `adopt` or `adopt-hotspot` with `temurin`, and replace `adopt-openj9` with `semeru`.